Follow-up Work

Investigate why the test is still panicking (in quick_shield() now).

On the zingolib side, I've tracked the error through to a call to librustzcash/zcash_client_backend::proto::service::compact_tx_streamer_client::CompactTxStreamerClient::send_transaction, which returns the following error on this commit, and is functional on the parent commit.

[/home/aloe/repos/zingo/zingolib/zingolib/src/grpc_connector.rs:362:9] client.send_transaction(request).await = Err(
    Status {
        code: Internal,
        message: "JsonRpcConnector error: Error: Serialization/Deserialization Error: missing field `result` at line 1 column 498",
        metadata: MetadataMap {
            headers: {
                "content-type": "application/grpc",
                "date": "Tue, 28 Jan 2025 19:29:26 GMT",
                "content-length": "0",
            },
        },
        source: None,
    },
)

Reproduced the same on my side.

thread 'wallet_basic::zebrad_send_to_transparent' panicked at integration-tests/tests/wallet_to_validator.rs:173:49:
called `Result::unwrap()` on an `Err` value: CompleteAndBroadcast(Broadcast(Broadcast("Send Error: status: Internal, message: \"JsonRpcConnector error: Error: Serialization/Deserialization Error: missing field `result` at line 1 column 498\", details: [], metadata: MetadataMap { headers: {\"content-type\": \"application/grpc\", \"date\": \"Tue, 28 Jan 2025 21:52:20 GMT\", \"content-length\": \"0\"} }")))
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
test wallet_basic::zebrad_send_to_transparent ... FAILED

it seems that zingolib is expecting something like

{ "result": {....}} 

and got something really different ? (see at line 1 column 498\")

@mergify requeue

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

• ❌ Unit tests / Test integration with lightwalletd
• ☑️ Build CD Docker / Build images
• ☑️ Get disk name / Get Mainnet cached disk
• ☑️ Test CD custom Docker config file / Test custom-conf in Docker
• ☑️ Test CD default Docker config file / Test default-conf in Docker
• ☑️ Test CD testnet Docker config file / Test testnet-conf in Docker

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue

@Mergifyio update

update

✅ Branch has been successfully updated

@mergify requeue

requeue

❌ This pull request head commit has not been previously disembarked from queue.

@mergify refresh

refresh

✅ Pull request refreshed

@mergify refresh

refresh

✅ Pull request refreshed